HP-DEC Networking Information The following statement explains HP's strategy for providing networking between HP and DEC computers. The statement is intended for internal HP audiences and should NOT be distributed to customers. This statement has been revised to include the position of the ASCENT*DNI product from Control Data Corporation (Integrated Information Systems). INTRODUCTION HP's DEC Connectivity Strategy is based on the convergence we see between the HP and DEC networking strategies and our belief that industry standard networking is the best foundation for a multivendor environment. We have been relying on our ability to convince customers to act in their best long term interests by augmenting DECnet with industry standard protocols. We have been quite successful with those customers who have identified the benefits of standard networking and are willing to take control of their network architecture by implementing a network based on standards rather than DEC proprietary protocols. DECnet Phase IV Environment Since our recommendations center around the coexistence of DECnet and TCP/IP networks, the main implementation vehicle becomes establishing one or more gateways between the two networks. These gateways are nodes which exist on both networks, and can be implemented in many different ways: * Add TCP/IP support to an existing VMS VAX running DECnet * Use an Ultrix VAX running TCP/IP and DECnet * Use an Apollo division DN Series Workstation running DECnet and TCP/IP * Use an HP 9000 Series 300 or 800 Workstation running DECnet and TCP/IP * Add NS/VAX support to an existing VMS VAX running DECnet For MPE V systems, this TCP/IP gateway can be a VAX/VMS system running NS/VAX software, a VAX/VMS system running ARPA software, or a VAX/Ultrix system running DECnet-ARPA gateway software. To utilize the ARPA-based gateways, the MPE V systems must run the Wollongong ARPA software. For MPE XL systems, the best gateway is a VAX/VMS system running NS/VAX. When ARPA services are available for MPE XL systems, the ARPA- based gateways can be used as well. Apollo division DN Series systems or HP 9000 workstations can be connected directly to DECnet Phase IV. The DN Series systems use the Apollo TECHnet product (LA 620), and the HP 9000 systems can use the ASCENT*DNI product available from Control Data Corporation (Integrated Information Systems). A DN Series or HP 9000 Series workstation equipped with this software can act as a gateway between the DECnet world and the TCP/IP world. The advantage of these gateways is that they require no additional software on any DEC system - the gateway could be provided completely by HP. For all customers, MPE V, MPE XL, HP-UX, and Domain/OS, HP's recommended approach is to utilize ARPA/TCP/IP today, with future migration to OSI. Our message remains "Use industry standard networking to implement multivendor environments." Not all customers are receptive to this message. DECnet Phase IV does not include TCP/IP support. DEC and several third parties do sell TCP/IP as a separate product, but DEC strongly discourages its use. Customers who base their networking architecture primarily on DEC's recommendations are thus reluctant to install TCP/IP. It is very difficult to sell HP's DEC connect strategy to these accounts prior to the release of DECnet Phase V. The Apollo TECHnet and ASCENT*DNI products offer an additional alternative for these accounts, and should be used in cases where the customer has a very high commitment to DECnet Phase IV, or a short term need for DECnet compatibility. Even with these customers we should point out the benefits of moving to standards-based networking. DECnet Phase V Environment Problem accounts will be much more receptive to the HP strategy when they have installed DECnet Phase V, scheduled for delivery within the next 6 months. The difference is that DECnet Phase V includes OSI and DEC recommends it for connection to non DEC systems. In fact, DEC is positioning DECnet Phase V as an OSI product. The HP strategy thus aligns with DEC's strategic recommendations. Of course, due to the anticipated long TCP/OSI coexistence period, many customers will elect to keep their current TCP/IP connections in the Phase V environment. HP will satisfy these customers by offering continued support for TCP/IP and providing OSI products which gracefully coexist with the TCP/IP products. Even in the Phase V environment, we will not satisfy all potential customers with the OSI strategy. OSI currently does not offer all the functionality of DECnet services. However, OSI functionality will improve with time, making the HP strategy progressively more acceptable. Other market forces, such as the GOSIP mandate from the U.S. Government and similar directives abroad will increase OSI appeal. We believe that DEC will be aggressive in encouraging their installed base to move to DECnet Phase V. This belief is supported by DEC statements at conferences and user group meetings and plans of accounts such as DuPont. As this movement to Phase V takes place, HP will be converging DOMAIN OS and HP-UX to a common operating system. HP does not plan to support DECnet on the converged operating system. We believe OSI will have evolved substantially by that time, reducing the demand for DECnet services enough that support will not be necessary. SUMMARY It is in the customer's best interest to implement multivendor environments using standard networking. In today's Phase IV environment we can connect all HP-UX and MPE systems with a variety of TCP/IP gateways (TCP/IP on VMS or Ultrix systems). DN Series and HP 9000 Series systems connect directly via the Apollo TECHnet and ASCENT*DNI products as well as via ARPA gateways. As DECnet Phase V becomes widely installed, the need for gateways or direct support of DECnet services will decrease. The HP Strategy of encouraging use of TCP/IP today and OSI in the future is supported by the comments of numerous industry analysts. We firmly believe that it best meets the needs of our customers. ### For more information on the ASCENT*DNI product you may contact Randy Barker at CDC at (513) 427-6379.